Tunnel: Clarify path forwarding and reverse proxy boundary - #33084
Open
hugo-vicente11 wants to merge 1 commit into
Open
Tunnel: Clarify path forwarding and reverse proxy boundary#33084hugo-vicente11 wants to merge 1 commit into
hugo-vicente11 wants to merge 1 commit into
Conversation
Contributor
Review✅ No issues found in commit Code ReviewThis code review is in beta and may not always be helpful — use your judgment. No code review issues found. ConventionsNo convention issues found. Style Guide ReviewNo style-guide issues found. CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR clarifies Cloudflare Tunnel request path behavior, emphasizing that cloudflared acts as a secure connector (not a reverse proxy) and forwards the full request path to the configured local service unless you explicitly rewrite paths at the edge or via a local reverse proxy.
Changes:
- Adds explicit “path forwarding” guidance to locally-managed tunnel configuration docs (including an example and alternatives for stripping/rewriting).
- Adds a “path routing” clarification note to the “add published application” flow.
- Updates Tunnel terminology pages to describe
cloudflaredas a connector daemon that does not rewrite paths.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/content/partials/cloudflare-one/tunnel/locally-managed/local-tunnel-terms.mdx | Clarifies ingress rule behavior by stating cloudflared forwards the full request path. |
| src/content/partials/cloudflare-one/tunnel/locally-managed/configuration-file.mdx | Adds a dedicated “Path forwarding” note describing matching vs forwarding and where to do rewrites/stripping. |
| src/content/partials/cloudflare-one/tunnel/add-published-application.mdx | Adds a note in the published application route steps clarifying that paths aren’t rewritten/stripped. |
| src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/tunnel-useful-terms.mdx | Adds connector framing: cloudflared as a daemon (not a reverse proxy) that doesn’t alter URI paths. |
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
hugo-vicente11
force-pushed
the
docs/tunnel-path-forwarding-boundary
branch
from
August 28, 2026 16:05
e8f9d8b to
94d3564
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Clarifies the architectural boundary between
cloudflared(as a secure connector daemon) and local reverse proxies across Cloudflare Tunnel documentation.Documentation checklist